Capturing and using design rationale

Capturing decisions and rationale from collaborative design

Design is, at its heart, a decision-making process. The decisions, alternative approaches considered, and the reasons behind the final choices are known as the Design Rationale (DR). The DR is usually not explicitly captured, at least not in an easily retrievable form. One way to reduce the effort in capturing rationale is to obtain the DR from unstructured documents and import it into a Ration...

Capturing Design Rationale for CE Teams

When an artifact is designed2 nowadays the typical output of this activity includes blueprints, CAD files, manufacturing plans and other documents describing the final result of a long series of deliberations and tradeoffs by the participants of concurrent engineering (CE) teams. The underlying intent and logical support (i.e.therationale ) for the decisions captured therein is usually lost, or...

Capturing Design Rationale in Concurrent Engineering Teams1

When an artifact is designed nowadays the typical output of this activity includes blueprints, CAD files, manufacturing plans and other documents describing the final result of a long series of deliberations and tradeoffs by the participants of concurrent engineering (CE) teams. The underlying intent and logical support (i.e.therationale ) for the decisions captured therein is usually lost, or ...

Capturing Design Rationale by Annotating E-mails

Development of a large and complex system, such as satellites, is a knowledge intensive task. Applying knowledge management to such a domain appears to lead to a more efficient development process. However, it has been reported that knowledge management suffers from capture bottleneck, i.e. lack of incentives for members of the community to invest time in sharing their resources, or knowledge. ...

t Capturing Design Rationale in Concurrent Engineering Teams